The Meeting That Ended Without a Decision

Six people, forty minutes, one item on the agenda: whether to move the enterprise tier from annual billing to quarterly.

The meeting goes well enough. Finance raises the revenue recognition question and gets a decent answer. Legal flags the notice period in the current terms, and someone writes it on the whiteboard. The head of sales, who initially opposed it, says he could live with it if the migration is opt-in for the first quarter.

At 10:51 somebody says, "Great, sounds like we're aligned."

Laptops close. Two people are already standing. Someone's phone is buzzing about the next call. The room is empty in under ninety seconds, and the mood is good because the argument is over and the argument was the hard part.

Eleven days later, the same item is on the same agenda, in the same room, with the same six people. Nothing was blocked. Nobody changed their mind. It simply never moved.

What was actually happening in those ninety seconds

Everyone walked out with a private, entirely reasonable model of what happens next.

• Legal was waiting on final commercial terms.
• Engineering was waiting on a ticket.
• Finance was waiting on the revised model.
• Sales was waiting to hear the opt-in was confirmed.

Every model was coherent. Every model assumed somebody else moved first.

The meeting produced an agreement and attached it to nobody, and an agreement with nobody attached to it behaves exactly like a decision that was never made, except it is quieter and more expensive.

This situation is not a niche failure. In a McKinsey Global Survey fielded in February 2018, only 20 percent of 1,259 respondents said their organizations excel at decision-making, and 61 percent said at least half the time spent making decisions was used ineffectively.

The pattern underneath

Your meetings have a designed beginning and an undesigned ending.

The beginning gets an invite, a time, an agenda, a pre-read, and a list of people who need to be there. The ending gets whatever fits in the seconds between "sounds like we're aligned." and the first person standing up. There's no protocol for that, so it fills with social noise: "Thanks, everyone. Good session. Let's keep the momentum."

Aviation solved a version of this problem decades ago, and the solution is almost insultingly simple. A controller telling an aircraft to hold short of a runway hasn't finished the job by saying it. Controllers must obtain a readback of all runway hold short instructions from the pilot. The instruction doesn't count as delivered until it comes back in the other person's voice. Not because pilots are careless. Because hearing what you expected to hear is a normal human failure, and the cost of it is a collision.

The last ninety seconds of your Tuesday meeting are your runway. Nobody dies, which is precisely why nobody built a procedure for it.

What to say at 10:52 next Tuesday

Four sentences, out loud, before anyone stands up.

• Say the name. "Priya owns this." One person said aloud in the room. Not written in the notes afterwards, not implied by seniority, not distributed across a function.
• Say the action that changes something observable. "Priya sends revised terms to legal. "Follow up," "circle back," and "pick this up" all describe nothing that anyone outside the conversation could see happening.
• Say the date and what happens if it passes. "By Thursday. If it hasn't gone by Thursday, it comes back here, and we name a different owner." A date with no consequence attached is decoration.
• Get the readback. Priya says it back in her own words. This is the part you'll want to ignore because it feels like you're checking homework. It's the part that catches the misunderstanding while everyone is still sitting down.

Then, within ten minutes, one line in the thread: owner, action, date. Ten minutes, because the version in your head at 11:02 is already softer than the version you agreed to at 10:52.

Where this goes wrong

There are a lot of ways this can go wrong. But let’s list the most obvious ones.

• You name the most senior person by default. They agree, because agreeing is faster than negotiating. Their calendar then becomes the ceiling on how quickly anything in your organization can happen.
• You name a function. "Marketing will pick this up." Marketing is eleven people, and eleven people is nobody.
• You name whoever does the work. The owner keeps the decision moving through legal, finance, and the release cycle. They perform very little of the actual work and overrule none of the experts. Those are two different jobs, and merging them means the busiest person carries both.
• You name someone who isn't in the room. Sameer discovered he owned a data migration when a colleague thanked him for owning it, sixteen days after the meeting. He'd been on leave that Tuesday. Nobody had told him, because everybody assumed somebody had.
• You skip the readback because these are adults. Pilots are adults. Surgeons are adults. The readback exists because certainty about what was heard is worth twenty seconds of mild awkwardness.

One thing this week

Pick your most repetitive recurring meeting. The one where items visit twice.

Book the last two minutes. Not as an agenda line, just as a thing you personally do: before anyone stands, say the name, the action, the date, and get it back in their voice.

You'll feel formal the first time. By the third week someone else will start doing it before you can.

A meeting ends when the talking stops. A decision starts when a person hears their own name and says it back.